LAN Server v3.04 LAN Server* Installation Notes for Intel's EtherExpress(TM) PRO/10 ISA LAN Adapter ====================================================================== Location of Driver: \NDIS\EPRO.OS2 (OS/2* driver) \NDIS\EPROEOS2.NIF or \NDIS\EPRO.DOS (DOS driver) \NDIS\EPROEDOS.NIF \NDIS\OEMSETUP.INF (for LAN Server 4.0 DOS client) Sample Configuration Files -------------------------- PROTOCOL.INI (will include): [EPRO_NIF] DriverName = EPRO$ IOADDRESS = 0x300 General Installation under OS/2 ------------------------------- 1 Verify the I/O Address of the EtherExpress PRO/10 adapter by running SoftSet2. 2 This installation does not use OS/2 Extended Services. These steps apply to both the file server and the workstation. After installing OS/2, follow the steps below prior to installing LAN Server 3.0 or the workstation requester. 3 Copy EPRO.OS2 and EPROEOS2.NIF from the EtherExpress PRO/10 LAN adapter configuration and driver diskette to the C:\IBMCOM\MACS directory. 4 Install LAN Adapter and Protocol Support (LAPS) from an OS/2 window. 5 After installing the software, select configure LAN transports. The EtherExpress PRO/10 adapter will appear in the LAN Adapters window. Select the necessary protocols and save the configuration. 6 Exit LAPS, shutdown the system and reboot the computer. The complete PROTOCOL.INI file will be created and put in the C:\IBMCOM directory. The CONFIG.SYS and AUTOEXEC.BAT files will be updated. General Installation under DOS for LAN Server 4.0 ------------------------------------------------- 1 Insert the LAN Server 4.0 DOS/Windows client disk 1 into drive A and type A:\INSTALL.EXE. 2 Specify the directory you want to install the DOS LAN requester files into, the default is C:\NET. 3 From the Select Network Adapter menu, choose "Network card not shown on list below..." 4 When prompted for the path of the OEM driver, insert the PRO/10 ISA adapter disk into drive a: and specify the path as "A:\NDIS". 5 Select the EtherExpress PRO/10 ISA adapter from the list. 6 Enter in a unique Machine Name for your workstation. 7 Enter in your User Name. 8 Enter the Domain Name that your workstation is attached to. 9 Specify which DOS LAN Services you want from the list: Graphical User Interface: Install GUI Peer Services: Install Peer Services Windows Support: Install Windows Support Protocol Driver: IBM NetBEUI 10 Verify the listed options are correct, then press "ENTER" to continue. 11 Verify the adapter settings are correct, and press "ENTER" to continue. 12 Exit to DOS from the install program on your computer by pressing "F3" after the installation is complete. General Installation under DOS for LAN Server 3.0 ------------------------------------------------- 1 Run DXMAID from the IBM OS/2 LAN Server v3.0 LAN Requester; LAN Support Program (LSP). 2 Complete environment information according to your needs. 3 Specify directory where EPRO.DOS and EPROEDOS.NIF are located. See driver location listing above for location on adapter disk 4 When DXMAID is completed, run INSTALL from DOS LAN Requester diskette. Note: LAN Requester needs DOS 3.3 through 5, but if you are on DOS 6.0 or above, SETVER can be used on the EXE files on the DOS LAN Requester disks. Hints and Tips -------------- 1 Parameters for the PROTOCOL.INI file: DRIVERNAME: (required) If you have a single adapter, use the syntax in the example above. If you are installing multiple adapters, each adapter must have a unique driver name. Additional instances of the driver would be referenced by DRIVERNAME=EPROx$, where "x" would be a unique number 2...9. IOADDRESS: (optional for single adapter systems - except when set to certain addresses noted below) This value must match the adapter's I/O address. If the driver does not find the adapter at the specified I/O address, it will scan most of the I/O addresses that the adapter could be at and will load if it finds the adapter. The only addresses the driver doesn't scan are 2E0, 2F0 or 370. If you have used one of these address, this parameter isn't optional. If you use multiple adapters in one machine, make sure you specify the correct IOADDRESS for each board. Otherwise, the driver will fail when loading on the second card. If you want information on advanced PROTOCOL.INI parameters, refer to the NDIS Driver Notes document; document 6341 on our automated services. * Third-party trademarks are the property of their respective owners.